Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca4e5f0ad2422e6228e16f512632869b7a5c109ebeefa3b395b7cc32d71d2cef

Tx prefix hash: bcde10d9fe7ee29156754f5dbb5d0f02a7fe28b8eb45112120c820842784491e
Tx public key: 7628acedb3bbd8ec5db2fb5184caaf0a80bc0fad432e6a3734009d7e005085ec
Timestamp: 1703008848 Timestamp [UCT]: 2023-12-19 18:00:48 Age [y:d:h:m:s]: 02:004:06:24:41
Block: 916698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522806 RingCT/type: yes/0
Extra: 017628acedb3bbd8ec5db2fb5184caaf0a80bc0fad432e6a3734009d7e005085ec021100000003e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35f9a50bf5aa52ff77a91cf3b1329bf52fb08059a31e4183a5482b5e1db7e3b9 0.600000000000 1374258 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": 916708, "vin": [ { "gen": { "height": 916698 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35f9a50bf5aa52ff77a91cf3b1329bf52fb08059a31e4183a5482b5e1db7e3b9" } } ], "extra": [ 1, 118, 40, 172, 237, 179, 187, 216, 236, 93, 178, 251, 81, 132, 202, 175, 10, 128, 188, 15, 173, 67, 46, 106, 55, 52, 0, 157, 126, 0, 80, 133, 236, 2, 17, 0, 0, 0, 3, 228, 187, 107, 131, 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