Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: a34fe29b10970d772b2edbee8f222579d19722df3fefafc6b954074688a7e47b

Tx prefix hash: d43e8faf3436862ca2859085f6d106b5c0b692608a28e72b8f681d53b2770409
Tx public key: 817ea8660306ffae2d1b65d75496c01f64be4b75a909754aaffd3e3ec3a2b7ca
Timestamp: 1710517103 Timestamp [UCT]: 2024-03-15 15:38:23 Age [y:d:h:m:s]: 00:258:03:59:58
Block: 978957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184807 RingCT/type: yes/0
Extra: 01817ea8660306ffae2d1b65d75496c01f64be4b75a909754aaffd3e3ec3a2b7ca0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22cb4b6966026c29767d0fba058a4d78a72dccfb29627faab6295834002407a4 0.600000000000 1438986 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 978967, "vin": [ { "gen": { "height": 978957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22cb4b6966026c29767d0fba058a4d78a72dccfb29627faab6295834002407a4" } } ], "extra": [ 1, 129, 126, 168, 102, 3, 6, 255, 174, 45, 27, 101, 215, 84, 150, 192, 31, 100, 190, 75, 117, 169, 9, 117, 74, 175, 253, 62, 62, 195, 162, 183, 202, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8