Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc19f0bf9fb8a3d1de8c0433c104dbf1a47ac5ed8c26c0d391a83aed15b0e99c

Tx prefix hash: 0f9c6025a97f3403bca8d5d89580a3ce65b2c7736f2516790db1ba7658211ded
Tx public key: 5d2124c382ca2b37252ae6cda9fe68fcf563cd071d3e2c19e57727eaf1e6e5f8
Timestamp: 1701728007 Timestamp [UCT]: 2023-12-04 22:13:27 Age [y:d:h:m:s]: 02:002:07:05:55
Block: 906070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521399 RingCT/type: yes/0
Extra: 015d2124c382ca2b37252ae6cda9fe68fcf563cd071d3e2c19e57727eaf1e6e5f8021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.610680338000 dcy

stealth address amount amount idx
00: f6677b451154b2f7e46f9bd3f1a69d999a017052f28e9abdb4292572702278c1 0.610680338000 1362991 of 0

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": 906080, "vin": [ { "gen": { "height": 906070 } } ], "vout": [ { "amount": 610680338, "target": { "key": "f6677b451154b2f7e46f9bd3f1a69d999a017052f28e9abdb4292572702278c1" } } ], "extra": [ 1, 93, 33, 36, 195, 130, 202, 43, 55, 37, 42, 230, 205, 169, 254, 104, 252, 245, 99, 205, 7, 29, 62, 44, 25, 229, 119, 39, 234, 241, 230, 229, 248, 2, 17, 0, 0, 0, 8, 230, 210, 127, 156, 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