Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 967d1dda40231eebf45997c96e086a0326085324206f66773ff280205748d5b3

Tx prefix hash: da5c14804de7cdda7bca5c3523c18cea3f2fca24b433bf44ee05a5ee93023d00
Tx public key: c7a74be73e1e4689356d588582aca00c14b8de0a1bfed2a839d6ac1417c698c1
Timestamp: 1715387467 Timestamp [UCT]: 2024-05-11 00:31:07 Age [y:d:h:m:s]: 01:036:05:26:07
Block: 1019336 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286715 RingCT/type: yes/0
Extra: 01c7a74be73e1e4689356d588582aca00c14b8de0a1bfed2a839d6ac1417c698c102110000000341ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 136a6665bc19b1a2d07f989e8827680d6487e09510a2a35b56e7bd8a9cb0e0e2 0.600000000000 1483277 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": 1019346, "vin": [ { "gen": { "height": 1019336 } } ], "vout": [ { "amount": 600000000, "target": { "key": "136a6665bc19b1a2d07f989e8827680d6487e09510a2a35b56e7bd8a9cb0e0e2" } } ], "extra": [ 1, 199, 167, 75, 231, 62, 30, 70, 137, 53, 109, 88, 133, 130, 172, 160, 12, 20, 184, 222, 10, 27, 254, 210, 168, 57, 214, 172, 20, 23, 198, 152, 193, 2, 17, 0, 0, 0, 3, 65, 238, 28, 155, 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