Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd76e4bac5eacefec8fe49335b74c124261358c4f0ebde0c249fc8a6158f39de

Tx prefix hash: 23eb28f283bd95f5a2e5e07f8b508c975b512a5dd68251be935b2ada05d45593
Tx public key: 979fc9a976be6e240aca8b3eee1c2dcbef0b59174a0b897f4d6cb9eba68043b3
Timestamp: 1714076514 Timestamp [UCT]: 2024-04-25 20:21:54 Age [y:d:h:m:s]: 00:305:09:34:40
Block: 1008441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218294 RingCT/type: yes/0
Extra: 01979fc9a976be6e240aca8b3eee1c2dcbef0b59174a0b897f4d6cb9eba68043b302110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8065c8ead175f243d461d35879d6283917b40725e4e7ac4f64f3baaa90ceb153 0.600000000000 1469911 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": 1008451, "vin": [ { "gen": { "height": 1008441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8065c8ead175f243d461d35879d6283917b40725e4e7ac4f64f3baaa90ceb153" } } ], "extra": [ 1, 151, 159, 201, 169, 118, 190, 110, 36, 10, 202, 139, 62, 238, 28, 45, 203, 239, 11, 89, 23, 74, 11, 137, 127, 77, 108, 185, 235, 166, 128, 67, 179, 2, 17, 0, 0, 0, 5, 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