Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b5c3261d06287cacb27916b62fce303c63860f42686a31578a92c40f5f642d3

Tx prefix hash: ed9c27f9779c9fcb98ab847501326fc7cc204a6bf60790c75e2606d3d924cf13
Tx public key: 7e8a00a1e52f48b6c51deff001add88e3c269586c07a4f198a13b1b7f28ef81f
Timestamp: 1725297940 Timestamp [UCT]: 2024-09-02 17:25:40 Age [y:d:h:m:s]: 00:254:00:20:10
Block: 1101481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181427 RingCT/type: yes/0
Extra: 017e8a00a1e52f48b6c51deff001add88e3c269586c07a4f198a13b1b7f28ef81f02110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1aca8c42391b497af11cc476ba807ffe079efa8e4f27fa90ee095bdb35c8c5ce 0.600000000000 1577548 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": 1101491, "vin": [ { "gen": { "height": 1101481 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1aca8c42391b497af11cc476ba807ffe079efa8e4f27fa90ee095bdb35c8c5ce" } } ], "extra": [ 1, 126, 138, 0, 161, 229, 47, 72, 182, 197, 29, 239, 240, 1, 173, 216, 142, 60, 38, 149, 134, 192, 122, 79, 25, 138, 19, 177, 183, 242, 142, 248, 31, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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