Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2b3e9c46786b26278242dde6d2796cc2e3b1a863dc7eaddfed20242e71fe7ff

Tx prefix hash: e4235a73727b50bb39196592692d6dadc6715d0c33b63cd2fd89358550c428a0
Tx public key: 9f3f7e8b1b3dc2eea704b7edcc9533c3f5437f124cca64ca5d43508b5bf22869
Timestamp: 1741451032 Timestamp [UCT]: 2025-03-08 16:23:52 Age [y:d:h:m:s]: 00:290:12:03:31
Block: 1234937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205402 RingCT/type: yes/0
Extra: 019f3f7e8b1b3dc2eea704b7edcc9533c3f5437f124cca64ca5d43508b5bf228690211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cbcd5f631f50711609a67b304833275570a6f19cbcbd09dc98bcd8ee81978c9 0.600000000000 1721872 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": 1234947, "vin": [ { "gen": { "height": 1234937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cbcd5f631f50711609a67b304833275570a6f19cbcbd09dc98bcd8ee81978c9" } } ], "extra": [ 1, 159, 63, 126, 139, 27, 61, 194, 238, 167, 4, 183, 237, 204, 149, 51, 195, 245, 67, 127, 18, 76, 202, 100, 202, 93, 67, 80, 139, 91, 242, 40, 105, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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