Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0937c9f4abc5cd3b718ee201637f898e4e1e0a019ecf196a5ca6d92f7cb9ca47

Tx prefix hash: f2503cc042928ed63386a70dbf2f81a87906a7b6408741d6883b0ab6d1a30cc5
Tx public key: d3fbe70a7318556132013ca8241b0e3d55493268fdaab3c2fdd4e2f81ead404f
Timestamp: 1708706174 Timestamp [UCT]: 2024-02-23 16:36:14 Age [y:d:h:m:s]: 01:301:14:05:16
Block: 963926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 474343 RingCT/type: yes/0
Extra: 01d3fbe70a7318556132013ca8241b0e3d55493268fdaab3c2fdd4e2f81ead404f0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 572ea3d792d3e5a210e67eb6ea40e640dd0ecf824eee19e4a291cde734ce6091 0.600000000000 1423653 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": 963936, "vin": [ { "gen": { "height": 963926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "572ea3d792d3e5a210e67eb6ea40e640dd0ecf824eee19e4a291cde734ce6091" } } ], "extra": [ 1, 211, 251, 231, 10, 115, 24, 85, 97, 50, 1, 60, 168, 36, 27, 14, 61, 85, 73, 50, 104, 253, 170, 179, 194, 253, 212, 226, 248, 30, 173, 64, 79, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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