Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cf6acb171d70a9e2d810ab8b7577988b38994cea701de178798a06684beb7cb

Tx prefix hash: f2e2514a18dd5429d244a74b3cdb2d214de4cbea1ca90f2289f67a1919805ef8
Tx public key: 657b6047dce56f75439f7993c9cb04ae7ba3ba4ea879baf3a2395b47fca4c9c1
Timestamp: 1709968552 Timestamp [UCT]: 2024-03-09 07:15:52 Age [y:d:h:m:s]: 01:063:07:43:41
Block: 974401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306263 RingCT/type: yes/0
Extra: 01657b6047dce56f75439f7993c9cb04ae7ba3ba4ea879baf3a2395b47fca4c9c102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e8246a533573e09005ed13c06885591dc9a7ac087a0a0830207223bd402be25 0.600000000000 1434356 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": 974411, "vin": [ { "gen": { "height": 974401 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e8246a533573e09005ed13c06885591dc9a7ac087a0a0830207223bd402be25" } } ], "extra": [ 1, 101, 123, 96, 71, 220, 229, 111, 117, 67, 159, 121, 147, 201, 203, 4, 174, 123, 163, 186, 78, 168, 121, 186, 243, 162, 57, 91, 71, 252, 164, 201, 193, 2, 17, 0, 0, 0, 1, 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