Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdebc815adf6f2f482e30ddbd2c672322cc923672ed8a982dd397f26088526e1

Tx prefix hash: 0e1d839bde2f0725ae299a1d9ca0396dd3e4f6a99956a285c9592cb4e6441d25
Tx public key: a28d241ec4389d376765445fd5d857432e9fa253f701b1beb30ace8be54cf0c3
Timestamp: 1730816405 Timestamp [UCT]: 2024-11-05 14:20:05 Age [y:d:h:m:s]: 01:006:01:55:37
Block: 1147138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262770 RingCT/type: yes/0
Extra: 01a28d241ec4389d376765445fd5d857432e9fa253f701b1beb30ace8be54cf0c30211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bb32013c56ea80415737d8feef9691d4e08b99c63da7769b063ac8aaf9025a4 0.600000000000 1631831 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": 1147148, "vin": [ { "gen": { "height": 1147138 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bb32013c56ea80415737d8feef9691d4e08b99c63da7769b063ac8aaf9025a4" } } ], "extra": [ 1, 162, 141, 36, 30, 196, 56, 157, 55, 103, 101, 68, 95, 213, 216, 87, 67, 46, 159, 162, 83, 247, 1, 177, 190, 179, 10, 206, 139, 229, 76, 240, 195, 2, 17, 0, 0, 0, 1, 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