Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a502fb3340ebae46368dbdf2915927064310866876fa63ee2defbfc13bdad99

Tx prefix hash: e1dcfc7c2e6da5549601071fdc13e5f3e6d0da041f788d914822ce11c8aa2c9d
Tx public key: 9733aa7acadb456ad57fc86d86f3182e3b523e82466636ee8e1620c4c9e54ce4
Timestamp: 1717499577 Timestamp [UCT]: 2024-06-04 11:12:57 Age [y:d:h:m:s]: 01:162:18:00:16
Block: 1036837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374893 RingCT/type: yes/0
Extra: 019733aa7acadb456ad57fc86d86f3182e3b523e82466636ee8e1620c4c9e54ce402110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2aaa711825be438edfd679f3a3c6f5162e5ad1ae364e971732b2b2b047b1d492 0.600000000000 1505366 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": 1036847, "vin": [ { "gen": { "height": 1036837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2aaa711825be438edfd679f3a3c6f5162e5ad1ae364e971732b2b2b047b1d492" } } ], "extra": [ 1, 151, 51, 170, 122, 202, 219, 69, 106, 213, 127, 200, 109, 134, 243, 24, 46, 59, 82, 62, 130, 70, 102, 54, 238, 142, 22, 32, 196, 201, 229, 76, 228, 2, 17, 0, 0, 0, 1, 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