Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8e680a54eef6266fe7ef90e5451c5eaec2e7fc00d64975ea118fa0d3d5deaeb

Tx prefix hash: a72221d1ae90f0232b27525eccbde5635b0c822370a0147f421321a2b2239f3e
Tx public key: e5c377d1236a2d3efd67f0d4a5bf16ae4cefd76bf876c263be541f2369e1f85e
Timestamp: 1719605514 Timestamp [UCT]: 2024-06-28 20:11:54 Age [y:d:h:m:s]: 01:175:10:38:36
Block: 1054270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384000 RingCT/type: yes/0
Extra: 01e5c377d1236a2d3efd67f0d4a5bf16ae4cefd76bf876c263be541f2369e1f85e02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7beaa85b6f914d63f9e1fc68873df9445bc417292435e7bbb80d43ad83631eb 0.600000000000 1524631 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": 1054280, "vin": [ { "gen": { "height": 1054270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7beaa85b6f914d63f9e1fc68873df9445bc417292435e7bbb80d43ad83631eb" } } ], "extra": [ 1, 229, 195, 119, 209, 35, 106, 45, 62, 253, 103, 240, 212, 165, 191, 22, 174, 76, 239, 215, 107, 248, 118, 194, 99, 190, 84, 31, 35, 105, 225, 248, 94, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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