Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f389816097972bff8146895c19b779aebf1865a8de8102c94e05c3e1657d2086

Tx prefix hash: 5300126f6bc0d1031bfc716759c87c99fecd70c3e062d6e0c7e3dc3bd27a9537
Tx public key: 0e4b51414f20d3af3bd361980c728703b5294e46fa99de726c9e6164d38b60e4
Timestamp: 1672927191 Timestamp [UCT]: 2023-01-05 13:59:51 Age [y:d:h:m:s]: 02:006:09:59:24
Block: 668157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 526490 RingCT/type: yes/0
Extra: 010e4b51414f20d3af3bd361980c728703b5294e46fa99de726c9e6164d38b60e402110000000452542ceb000000000000000000

1 output(s) for total of 3.750752900000 dcy

stealth address amount amount idx
00: eeb98f7a0ba3ec9c5c5b697ca337405f79b107f47b5d1bfbc50e600bd5cb289f 3.750752900000 1109390 of 0

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": 668167, "vin": [ { "gen": { "height": 668157 } } ], "vout": [ { "amount": 3750752900, "target": { "key": "eeb98f7a0ba3ec9c5c5b697ca337405f79b107f47b5d1bfbc50e600bd5cb289f" } } ], "extra": [ 1, 14, 75, 81, 65, 79, 32, 211, 175, 59, 211, 97, 152, 12, 114, 135, 3, 181, 41, 78, 70, 250, 153, 222, 114, 108, 158, 97, 100, 211, 139, 96, 228, 2, 17, 0, 0, 0, 4, 82, 84, 44, 235, 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