Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51ce63a0cf014486583632400dc25ecb76de404de04f5159808bdf7caac6c8f8

Tx prefix hash: 462ae57f8373aa0a0f3d3bb1afce87e9477fe39dd409befa9689f32972ff0092
Tx public key: be36a1fbaafedc72688f8d4c0ce0bd0a2cb3abded1e38dc5d8216423e191b4ff
Timestamp: 1751418556 Timestamp [UCT]: 2025-07-02 01:09:16 Age [y:d:h:m:s]: 00:139:08:08:23
Block: 1316886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97828 RingCT/type: yes/0
Extra: 01be36a1fbaafedc72688f8d4c0ce0bd0a2cb3abded1e38dc5d8216423e191b4ff02110000000301491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04af1f649308e23385eda8a5fbfcd1b74d3edc5118ca61efb57a0a586f630eb9 0.600000000000 1804549 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": 1316896, "vin": [ { "gen": { "height": 1316886 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04af1f649308e23385eda8a5fbfcd1b74d3edc5118ca61efb57a0a586f630eb9" } } ], "extra": [ 1, 190, 54, 161, 251, 170, 254, 220, 114, 104, 143, 141, 76, 12, 224, 189, 10, 44, 179, 171, 222, 209, 227, 141, 197, 216, 33, 100, 35, 225, 145, 180, 255, 2, 17, 0, 0, 0, 3, 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