Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcee876dd49948ed5053bf3910efa07f2e813960538c0b35508681f91f4cd5ff

Tx prefix hash: fe4161de092cb83c1ead37e24e17095a941f2c3956e7fd96706aadb37201de99
Tx public key: 07beb7590a90edcb4a47e140eafe7dcb0dc9c7897df070548bec1533f541b075
Timestamp: 1751774412 Timestamp [UCT]: 2025-07-06 04:00:12 Age [y:d:h:m:s]: 00:209:16:49:03
Block: 1319685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148174 RingCT/type: yes/0
Extra: 0107beb7590a90edcb4a47e140eafe7dcb0dc9c7897df070548bec1533f541b07502110000000501491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5cdb2780c3d4db7c582ce0bfcdf6b3b1c8a88a1c57ceeac7a211150cd35479b9 0.600000000000 1807378 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": 1319695, "vin": [ { "gen": { "height": 1319685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5cdb2780c3d4db7c582ce0bfcdf6b3b1c8a88a1c57ceeac7a211150cd35479b9" } } ], "extra": [ 1, 7, 190, 183, 89, 10, 144, 237, 203, 74, 71, 225, 64, 234, 254, 125, 203, 13, 201, 199, 137, 125, 240, 112, 84, 139, 236, 21, 51, 245, 65, 176, 117, 2, 17, 0, 0, 0, 5, 1, 73, 31, 136, 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