Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 869adef23f8ef2654dc5548566d51b9a8d40636eec19fb31460ca4dc666972d3

Tx prefix hash: ce5d47226542ff1392b710f604e0a9b7be32158bdc1ef47bd00f1d65d7667bfe
Tx public key: 04a3b4cb1d3515a8beec0f97504594680fee743afb7e13b748c7fb8dde437a10
Timestamp: 1718754843 Timestamp [UCT]: 2024-06-18 23:54:03 Age [y:d:h:m:s]: 01:143:01:57:44
Block: 1047232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360814 RingCT/type: yes/0
Extra: 0104a3b4cb1d3515a8beec0f97504594680fee743afb7e13b748c7fb8dde437a1002110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd20c376af150a8319f8424fbae93389d022802b856e119f1b7510f6362a7275 0.600000000000 1517051 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": 1047242, "vin": [ { "gen": { "height": 1047232 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd20c376af150a8319f8424fbae93389d022802b856e119f1b7510f6362a7275" } } ], "extra": [ 1, 4, 163, 180, 203, 29, 53, 21, 168, 190, 236, 15, 151, 80, 69, 148, 104, 15, 238, 116, 58, 251, 126, 19, 183, 72, 199, 251, 141, 222, 67, 122, 16, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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