Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc3408e5c03e4e6b36e47ff7e261e857c0133df6ac25851ef7edab51f3c93daa

Tx prefix hash: 8845f8dec7a7d5bce17e0f5dbf0ea65f29ef871fd1efa281753feb57fe985f5b
Tx public key: b6f37b052f515c992082b5f768493f9d788a115e9006e9cee7506f4fa10f38b7
Timestamp: 1732330877 Timestamp [UCT]: 2024-11-23 03:01:17 Age [y:d:h:m:s]: 00:000:18:19:27
Block: 1159688 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 543 RingCT/type: yes/0
Extra: 01b6f37b052f515c992082b5f768493f9d788a115e9006e9cee7506f4fa10f38b7021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d520762b0afc9ebaa9e516a2d1b333cd4705d68134f3c0554f43e351b06af7a7 0.600000000000 1645327 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": 1159698, "vin": [ { "gen": { "height": 1159688 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d520762b0afc9ebaa9e516a2d1b333cd4705d68134f3c0554f43e351b06af7a7" } } ], "extra": [ 1, 182, 243, 123, 5, 47, 81, 92, 153, 32, 130, 181, 247, 104, 73, 63, 157, 120, 138, 17, 94, 144, 6, 233, 206, 231, 80, 111, 79, 161, 15, 56, 183, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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