Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d546b94f7b1e9e5dc4c50e6034586115c21f1f2323523ca20e663f913a73bbc3

Tx prefix hash: 5a52214fc78d6f170df07bc07586cc49e943d6c5fc3087ba7fc1837c0acf8906
Tx public key: b56b0882aee5a2cd3a381582ea7df7883cfc30a5f87bda2224cdb3ed24152072
Timestamp: 1741598613 Timestamp [UCT]: 2025-03-10 09:23:33 Age [y:d:h:m:s]: 00:211:11:24:24
Block: 1236163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148808 RingCT/type: yes/0
Extra: 01b56b0882aee5a2cd3a381582ea7df7883cfc30a5f87bda2224cdb3ed241520720211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f826fbb31072b2f8cdb082e96459a47f91d89db599154ceba238ecf86f166fe5 0.600000000000 1723108 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": 1236173, "vin": [ { "gen": { "height": 1236163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f826fbb31072b2f8cdb082e96459a47f91d89db599154ceba238ecf86f166fe5" } } ], "extra": [ 1, 181, 107, 8, 130, 174, 229, 162, 205, 58, 56, 21, 130, 234, 125, 247, 136, 60, 252, 48, 165, 248, 123, 218, 34, 36, 205, 179, 237, 36, 21, 32, 114, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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