Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2898a26b345298b768509f60b5a36e69bbf3590180ec9e80fc7f51d000c62378

Tx prefix hash: 01cea16bd44a133c4cc5ae2fbcf19657e6f452c5b0a0c5aad059e15d739d7986
Tx public key: a724818f0a1be8939b67b4f63d3f7340371ff3e30e0c0213e1c925d86c4172dd
Timestamp: 1710089577 Timestamp [UCT]: 2024-03-10 16:52:57 Age [y:d:h:m:s]: 00:228:23:32:15
Block: 975406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163966 RingCT/type: yes/0
Extra: 01a724818f0a1be8939b67b4f63d3f7340371ff3e30e0c0213e1c925d86c4172dd02110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d71f78b17b534331a0e804355d896c4130382ed72aeae0d8a960c98e27c26df1 0.600000000000 1435377 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": 975416, "vin": [ { "gen": { "height": 975406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d71f78b17b534331a0e804355d896c4130382ed72aeae0d8a960c98e27c26df1" } } ], "extra": [ 1, 167, 36, 129, 143, 10, 27, 232, 147, 155, 103, 180, 246, 61, 63, 115, 64, 55, 31, 243, 227, 14, 12, 2, 19, 225, 201, 37, 216, 108, 65, 114, 221, 2, 17, 0, 0, 0, 10, 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