Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8877c9e1f015da068938fafbf94b499a8b62454e45be1e5d609557c8d048fd8c

Tx prefix hash: 86306e42efa57242d1e9f2a6b024be68c2ddbdac179938cb7476569566b923ac
Tx public key: 434ea1e1a875e73eb7d9f9a48e5c219585c47b15af2019e793421aa3c49e9685
Timestamp: 1646551801 Timestamp [UCT]: 2022-03-06 07:30:01 Age [y:d:h:m:s]: 03:239:19:22:14
Block: 452389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 949252 RingCT/type: yes/0
Extra: 01434ea1e1a875e73eb7d9f9a48e5c219585c47b15af2019e793421aa3c49e968502110000000fbf7ee4e7000000000000000000

1 output(s) for total of 19.455738602000 dcy

stealth address amount amount idx
00: b59df7dc74e6ff0c0d80baf80c655d207233768f044b4f28674dd5679423c1bb 19.455738602000 867698 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": 452399, "vin": [ { "gen": { "height": 452389 } } ], "vout": [ { "amount": 19455738602, "target": { "key": "b59df7dc74e6ff0c0d80baf80c655d207233768f044b4f28674dd5679423c1bb" } } ], "extra": [ 1, 67, 78, 161, 225, 168, 117, 231, 62, 183, 217, 249, 164, 142, 92, 33, 149, 133, 196, 123, 21, 175, 32, 25, 231, 147, 66, 26, 163, 196, 158, 150, 133, 2, 17, 0, 0, 0, 15, 191, 126, 228, 231, 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