Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ae6361a6da2a7fe95be39d056be899275dc8fcacbcde88c9e093fdccc4ec646

Tx prefix hash: ccc305c8d87c8f24eb26ab0b003c9e69bfdde10e4848b866a3ca7bae235b0fc9
Tx public key: dd501bf5e2ed5d940e56886f246d75d571955cf073335d46750276d243bd3a54
Timestamp: 1702744474 Timestamp [UCT]: 2023-12-16 16:34:34 Age [y:d:h:m:s]: 01:026:20:09:47
Block: 914495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280531 RingCT/type: yes/0
Extra: 01dd501bf5e2ed5d940e56886f246d75d571955cf073335d46750276d243bd3a5402110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fe03ac9772c4c1174e52d755fbcb00914c31ff59dc40e8e5a6d9bc1bbd29f22 0.600000000000 1371811 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": 914505, "vin": [ { "gen": { "height": 914495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fe03ac9772c4c1174e52d755fbcb00914c31ff59dc40e8e5a6d9bc1bbd29f22" } } ], "extra": [ 1, 221, 80, 27, 245, 226, 237, 93, 148, 14, 86, 136, 111, 36, 109, 117, 213, 113, 149, 92, 240, 115, 51, 93, 70, 117, 2, 118, 210, 67, 189, 58, 84, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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