Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fc866e290ed37de9f72d30aaf47d7810994560a85cf6122fbb19d83aac06042

Tx prefix hash: 1c7b21c62ea8bca6d88c97e7d247749c3f533d724d8b59379f1d254dba781468
Tx public key: 5aa34ecbbba8f002357b35adb1a42a17492b91d56caba1141e3185c33329cdd8
Timestamp: 1648282723 Timestamp [UCT]: 2022-03-26 08:18:43 Age [y:d:h:m:s]: 02:233:02:21:04
Block: 466670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 686088 RingCT/type: yes/0
Extra: 015aa34ecbbba8f002357b35adb1a42a17492b91d56caba1141e3185c33329cdd802110000001a4a0f5013000000000000000000

1 output(s) for total of 17.447323773000 dcy

stealth address amount amount idx
00: a0f99be7cac7065d2e362c789621e95b34801da8a4d4a8c8ee4cd12778c6e6ec 17.447323773000 885031 of 0

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": 466680, "vin": [ { "gen": { "height": 466670 } } ], "vout": [ { "amount": 17447323773, "target": { "key": "a0f99be7cac7065d2e362c789621e95b34801da8a4d4a8c8ee4cd12778c6e6ec" } } ], "extra": [ 1, 90, 163, 78, 203, 187, 168, 240, 2, 53, 123, 53, 173, 177, 164, 42, 23, 73, 43, 145, 213, 108, 171, 161, 20, 30, 49, 133, 195, 51, 41, 205, 216, 2, 17, 0, 0, 0, 26, 74, 15, 80, 19, 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