Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c954eb2e06019149ab3e9a4b7cef992e6ee57f2d077b183831aa7865451a84aa

Tx prefix hash: 9710a3be7322192f0d069eea731bd971b17caffd6dfc3db668b82637f1eac3f0
Tx public key: 6524a4eb0a4f48bd3e58de758681dc10d6261a1ca4081eda4240567b859b946b
Timestamp: 1713711723 Timestamp [UCT]: 2024-04-21 15:02:03 Age [y:d:h:m:s]: 01:192:11:24:51
Block: 1005412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396216 RingCT/type: yes/0
Extra: 016524a4eb0a4f48bd3e58de758681dc10d6261a1ca4081eda4240567b859b946b02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae53ed15feac21c9d57931381b387f5baca63f1df40a78d0474c1dc6688c6e51 0.600000000000 1466092 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": 1005422, "vin": [ { "gen": { "height": 1005412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae53ed15feac21c9d57931381b387f5baca63f1df40a78d0474c1dc6688c6e51" } } ], "extra": [ 1, 101, 36, 164, 235, 10, 79, 72, 189, 62, 88, 222, 117, 134, 129, 220, 16, 214, 38, 26, 28, 164, 8, 30, 218, 66, 64, 86, 123, 133, 155, 148, 107, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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