Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af4a73308b2b4974d7a3f62f7966f6b7d0853b6fc9800b8fdb61d71e1ad2d0c1

Tx prefix hash: e8a1f3a99d279cb568a8c71b9c98362fd419d3e3a40c717405233342efa2271d
Tx public key: b95c646fd7860345678896ce6806b1f4db1c16168a5dd1f792a42f0903617bb5
Timestamp: 1750743217 Timestamp [UCT]: 2025-06-24 05:33:37 Age [y:d:h:m:s]: 00:197:06:15:31
Block: 1311608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138983 RingCT/type: yes/0
Extra: 01b95c646fd7860345678896ce6806b1f4db1c16168a5dd1f792a42f0903617bb5021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e84dad3d4059f54041761ae657de7d4f7420a7e317f659ccbd513864146ba33 0.600000000000 1799235 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": 1311618, "vin": [ { "gen": { "height": 1311608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e84dad3d4059f54041761ae657de7d4f7420a7e317f659ccbd513864146ba33" } } ], "extra": [ 1, 185, 92, 100, 111, 215, 134, 3, 69, 103, 136, 150, 206, 104, 6, 177, 244, 219, 28, 22, 22, 138, 93, 209, 247, 146, 164, 47, 9, 3, 97, 123, 181, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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