Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23de10857a28fc22bd61c37e008f5a312e3cd89f3665bb248d95987005138170

Tx prefix hash: ececd892fec6b5ea28d4cfa740c6ed95204a09e26e4fb3f8e277fdbff2105267
Tx public key: abe6bf7453bf0240e6669fcf6c3ffb16b5e252e4d17f22b4f404b91a69473be6
Timestamp: 1708405015 Timestamp [UCT]: 2024-02-20 04:56:55 Age [y:d:h:m:s]: 01:050:20:59:27
Block: 961428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297387 RingCT/type: yes/0
Extra: 01abe6bf7453bf0240e6669fcf6c3ffb16b5e252e4d17f22b4f404b91a69473be602110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1c0a12c2f553fc365411908f4b1cc29df8f231ebdd002484c2d88910f1853b9 0.600000000000 1421037 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": 961438, "vin": [ { "gen": { "height": 961428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1c0a12c2f553fc365411908f4b1cc29df8f231ebdd002484c2d88910f1853b9" } } ], "extra": [ 1, 171, 230, 191, 116, 83, 191, 2, 64, 230, 102, 159, 207, 108, 63, 251, 22, 181, 226, 82, 228, 209, 127, 34, 180, 244, 4, 185, 26, 105, 71, 59, 230, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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