Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fe7b5010b19e2986a09690e8bf9319bf7f40761dc9148d2f9ae6c74fc0bcbe0

Tx prefix hash: cb15954c60548aee92b075c4158b326bc23e7601934e9cace33179e365350167
Tx public key: 7b413b76384975eb88b24909f785c51b7f3f50ff577c9cb0e8bd07e952250041
Timestamp: 1734901089 Timestamp [UCT]: 2024-12-22 20:58:09 Age [y:d:h:m:s]: 00:177:14:43:55
Block: 1181006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126629 RingCT/type: yes/0
Extra: 017b413b76384975eb88b24909f785c51b7f3f50ff577c9cb0e8bd07e95225004102110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 076a4b59d56ff5e8fec5b2ef26feaca39c50dc8be4e5aafc1cd1d64bd4875b1c 0.600000000000 1667421 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": 1181016, "vin": [ { "gen": { "height": 1181006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "076a4b59d56ff5e8fec5b2ef26feaca39c50dc8be4e5aafc1cd1d64bd4875b1c" } } ], "extra": [ 1, 123, 65, 59, 118, 56, 73, 117, 235, 136, 178, 73, 9, 247, 133, 197, 27, 127, 63, 80, 255, 87, 124, 156, 176, 232, 189, 7, 233, 82, 37, 0, 65, 2, 17, 0, 0, 0, 10, 31, 10, 83, 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