Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcbfa4f45f3fe90dc1ec3348abeb47b996ff05f4ae2237feb9c6df69d3366d2e

Tx prefix hash: cd14a8aff973ef9448057885997246138355c1e9cc12855a0692a167a123c12e
Tx public key: 119d4b7d8b615cee39f9d91cff19e26342bfc41d594293fb32e8e42cde04858f
Timestamp: 1725359482 Timestamp [UCT]: 2024-09-03 10:31:22 Age [y:d:h:m:s]: 00:215:00:12:59
Block: 1101995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153509 RingCT/type: yes/0
Extra: 01119d4b7d8b615cee39f9d91cff19e26342bfc41d594293fb32e8e42cde04858f021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdee2d3bd9d1c6df8e6065f3c4993386b398a25cf575b2155610c7927b34a137 0.600000000000 1578258 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": 1102005, "vin": [ { "gen": { "height": 1101995 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdee2d3bd9d1c6df8e6065f3c4993386b398a25cf575b2155610c7927b34a137" } } ], "extra": [ 1, 17, 157, 75, 125, 139, 97, 92, 238, 57, 249, 217, 28, 255, 25, 226, 99, 66, 191, 196, 29, 89, 66, 147, 251, 50, 232, 228, 44, 222, 4, 133, 143, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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