Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d813cb08b06e728bf56b5ec4c50b66488366d40034723f73c5180b9fd0c4e44

Tx prefix hash: 50e6ecdcf9bd35e428e3b64a7f4081ed08d16c1ab2e4d00cd3113372cc4756e7
Tx public key: 25cc264e5c93b5a0513d321aae81daf33ed95c8412cf90bf99c4e8fa5413d67e
Timestamp: 1724013196 Timestamp [UCT]: 2024-08-18 20:33:16 Age [y:d:h:m:s]: 00:228:18:13:03
Block: 1090834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163361 RingCT/type: yes/0
Extra: 0125cc264e5c93b5a0513d321aae81daf33ed95c8412cf90bf99c4e8fa5413d67e021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9ad663916b7c097dfd4e3361f1b84ed2880349fa35a02195278b5c2de5f4c85 0.600000000000 1565459 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": 1090844, "vin": [ { "gen": { "height": 1090834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9ad663916b7c097dfd4e3361f1b84ed2880349fa35a02195278b5c2de5f4c85" } } ], "extra": [ 1, 37, 204, 38, 78, 92, 147, 181, 160, 81, 61, 50, 26, 174, 129, 218, 243, 62, 217, 92, 132, 18, 207, 144, 191, 153, 196, 232, 250, 84, 19, 214, 126, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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