Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 271b0148025ded5f2e7a2e4ed87a656b13b61b04b0197a6d08220e6e666f748c

Tx prefix hash: 9ebaa2f23e5ff56732a69aa2d209f4133c12c8ed020124382157b3300a02460c
Tx public key: cf31d7a4d7c9d0f39701cb530a56df97011cc4373b89e06d404cb06d05687235
Timestamp: 1765995311 Timestamp [UCT]: 2025-12-17 18:15:11 Age [y:d:h:m:s]: 00:043:09:29:50
Block: 1435738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30900 RingCT/type: yes/0
Extra: 01cf31d7a4d7c9d0f39701cb530a56df97011cc4373b89e06d404cb06d0568723502110000000170609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d04863e503fe7521573e2fcda7b89ec716eb3b0ae5633edfce6c97dae0240aa1 0.600000000000 1924537 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": 1435748, "vin": [ { "gen": { "height": 1435738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d04863e503fe7521573e2fcda7b89ec716eb3b0ae5633edfce6c97dae0240aa1" } } ], "extra": [ 1, 207, 49, 215, 164, 215, 201, 208, 243, 151, 1, 203, 83, 10, 86, 223, 151, 1, 28, 196, 55, 59, 137, 224, 109, 64, 76, 176, 109, 5, 104, 114, 53, 2, 17, 0, 0, 0, 1, 112, 96, 157, 3, 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