Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d0b1a437839a0117c69f7bd3a26e64fcf989a3d1850de6ea8038d4dc42e041e

Tx prefix hash: 0421a379dbe1b984f1969f4d4f6807b5c47acfa290c458581f94fa126f7c5de3
Tx public key: 894cd3451c9ede9fa95ea06aabf510916dce2d473561b376ef58ecb71ef255d7
Timestamp: 1702064832 Timestamp [UCT]: 2023-12-08 19:47:12 Age [y:d:h:m:s]: 01:116:07:33:48
Block: 908862 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344265 RingCT/type: yes/0
Extra: 01894cd3451c9ede9fa95ea06aabf510916dce2d473561b376ef58ecb71ef255d7021100000004faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68af67f2f40b06f29842a7ae3ae057969f1f5e57270bf8d26ba7342ad1a21789 0.600000000000 1365919 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": 908872, "vin": [ { "gen": { "height": 908862 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68af67f2f40b06f29842a7ae3ae057969f1f5e57270bf8d26ba7342ad1a21789" } } ], "extra": [ 1, 137, 76, 211, 69, 28, 158, 222, 159, 169, 94, 160, 106, 171, 245, 16, 145, 109, 206, 45, 71, 53, 97, 179, 118, 239, 88, 236, 183, 30, 242, 85, 215, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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