Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8fc452e9ce9b98811b36e188d7e953710a603bc023487f36a2c4ee44e568fe8

Tx prefix hash: 377af648ed2dfd00d8cf1644189f6217dcbeeca8942f8cb7a51f3477b81681d2
Tx public key: dbec37bc82ee8d97eca9fb7c4676bef25f17ed4169f062c702fb5e81c75f6cc5
Timestamp: 1719886579 Timestamp [UCT]: 2024-07-02 02:16:19 Age [y:d:h:m:s]: 00:276:18:47:05
Block: 1056615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197764 RingCT/type: yes/0
Extra: 01dbec37bc82ee8d97eca9fb7c4676bef25f17ed4169f062c702fb5e81c75f6cc50211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d605f8d0c46e3747d062ba631a9bdcd8114815dca5b1ec7a57a4789c36c8fc7 0.600000000000 1527030 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": 1056625, "vin": [ { "gen": { "height": 1056615 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d605f8d0c46e3747d062ba631a9bdcd8114815dca5b1ec7a57a4789c36c8fc7" } } ], "extra": [ 1, 219, 236, 55, 188, 130, 238, 141, 151, 236, 169, 251, 124, 70, 118, 190, 242, 95, 23, 237, 65, 105, 240, 98, 199, 2, 251, 94, 129, 199, 95, 108, 197, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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