Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be34ba4e8fe53cf814a82ecd891440f59ebe16d20727279264af1a7f319c1608

Tx prefix hash: 72bd9e89bd7b9f979f6865b45e756dc55cb778907db6c0c778f381a80a12efa7
Tx public key: 0cf2e09dfb4f87b0733d76685aee7ff02fbaa1a72d6920c644a907c6e42899a3
Timestamp: 1757115354 Timestamp [UCT]: 2025-09-05 23:35:54 Age [y:d:h:m:s]: 00:123:12:33:03
Block: 1362230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88377 RingCT/type: yes/0
Extra: 010cf2e09dfb4f87b0733d76685aee7ff02fbaa1a72d6920c644a907c6e42899a302110000000cb2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5862a766008f203dd44428a9aad54b1bfb5a7616cd718f1f9ea78e55003bd923 0.600000000000 1850261 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": 1362240, "vin": [ { "gen": { "height": 1362230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5862a766008f203dd44428a9aad54b1bfb5a7616cd718f1f9ea78e55003bd923" } } ], "extra": [ 1, 12, 242, 224, 157, 251, 79, 135, 176, 115, 61, 118, 104, 90, 238, 127, 240, 47, 186, 161, 167, 45, 105, 32, 198, 68, 169, 7, 198, 228, 40, 153, 163, 2, 17, 0, 0, 0, 12, 178, 247, 132, 196, 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