Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4aecaa0f763d3c49782297c59b89a7f1a1833b8d77c0f3297221f83c31b65ea

Tx prefix hash: 34e7e96e6e7b0a197a0933167d6955c24992c4e0c0494ddc1455379ee60327ac
Tx public key: b26141d0256df1ab169db4938a016d3f0b0272cd44aa55db15ea45687cb8133e
Timestamp: 1737548798 Timestamp [UCT]: 2025-01-22 12:26:38 Age [y:d:h:m:s]: 00:148:12:45:08
Block: 1202848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105875 RingCT/type: yes/0
Extra: 01b26141d0256df1ab169db4938a016d3f0b0272cd44aa55db15ea45687cb8133e021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37ad70e956fd334556b3141652300562ee86e70d58bbf549d09a4e10e258d8d3 0.600000000000 1689515 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": 1202858, "vin": [ { "gen": { "height": 1202848 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37ad70e956fd334556b3141652300562ee86e70d58bbf549d09a4e10e258d8d3" } } ], "extra": [ 1, 178, 97, 65, 208, 37, 109, 241, 171, 22, 157, 180, 147, 138, 1, 109, 63, 11, 2, 114, 205, 68, 170, 85, 219, 21, 234, 69, 104, 124, 184, 19, 62, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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