Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36c227a75d28c0e3e9b9791b0f7cbe6939dbdb04f18af88f060ad56bb9b2a116

Tx prefix hash: 2062df3c5215cbef6d62d0c38f09697f68f6e9aac4483b5caa7bf1182f0ff9c6
Tx public key: 541da79d4429eab566a3df6991810b3de946857c8b37160fa159736f65815e97
Timestamp: 1719132217 Timestamp [UCT]: 2024-06-23 08:43:37 Age [y:d:h:m:s]: 01:140:09:10:53
Block: 1050346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358890 RingCT/type: yes/0
Extra: 01541da79d4429eab566a3df6991810b3de946857c8b37160fa159736f65815e970211000000080fbbc4c5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38b64b1ef6155404d0b5a061148862f754e91a533d9b9cefee22e645e8ca95dd 0.600000000000 1520511 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": 1050356, "vin": [ { "gen": { "height": 1050346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38b64b1ef6155404d0b5a061148862f754e91a533d9b9cefee22e645e8ca95dd" } } ], "extra": [ 1, 84, 29, 167, 157, 68, 41, 234, 181, 102, 163, 223, 105, 145, 129, 11, 61, 233, 70, 133, 124, 139, 55, 22, 15, 161, 89, 115, 111, 101, 129, 94, 151, 2, 17, 0, 0, 0, 8, 15, 187, 196, 197, 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