Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 404488915117bfbe9ab2c3604fac10e87db1464da0017d082e7908717c1f3c2c

Tx prefix hash: b23bb2691e113976142643c15090f3421ec3ed2b874b4dfda8c53ecf3889a42d
Tx public key: 41a7fc65c0784747ebd67f7f00f636d22e682ceaf1b7f3d615d01df6e5db415e
Timestamp: 1722295668 Timestamp [UCT]: 2024-07-29 23:27:48 Age [y:d:h:m:s]: 01:101:08:29:52
Block: 1076580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330935 RingCT/type: yes/0
Extra: 0141a7fc65c0784747ebd67f7f00f636d22e682ceaf1b7f3d615d01df6e5db415e02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 054ddeb41f5e526c3a87f8e99941594141950f4f2bcf6fbd276dca78d189e9e5 0.600000000000 1549119 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": 1076590, "vin": [ { "gen": { "height": 1076580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "054ddeb41f5e526c3a87f8e99941594141950f4f2bcf6fbd276dca78d189e9e5" } } ], "extra": [ 1, 65, 167, 252, 101, 192, 120, 71, 71, 235, 214, 127, 127, 0, 246, 54, 210, 46, 104, 44, 234, 241, 183, 243, 214, 21, 208, 29, 246, 229, 219, 65, 94, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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