Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bef3892f4530ee2ca005341f4d2a9db079e7db6f3e86d682270de7957f43dc0

Tx prefix hash: e3ce849b530354b2e57c205c6f682d4f47bca288e25eddd78690a541540fb48d
Tx public key: 8af1bc3d56a41db0c5aa89ce000abdce6fe1ef39ddb1052fc5cb1971c5ae1d9c
Timestamp: 1719062397 Timestamp [UCT]: 2024-06-22 13:19:57 Age [y:d:h:m:s]: 00:286:20:34:45
Block: 1049762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205000 RingCT/type: yes/0
Extra: 018af1bc3d56a41db0c5aa89ce000abdce6fe1ef39ddb1052fc5cb1971c5ae1d9c0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 026c5fd90a8d7465110920cf20e6c003f773f48398af09c956e6f59f2e965546 0.600000000000 1519867 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": 1049772, "vin": [ { "gen": { "height": 1049762 } } ], "vout": [ { "amount": 600000000, "target": { "key": "026c5fd90a8d7465110920cf20e6c003f773f48398af09c956e6f59f2e965546" } } ], "extra": [ 1, 138, 241, 188, 61, 86, 164, 29, 176, 197, 170, 137, 206, 0, 10, 189, 206, 111, 225, 239, 57, 221, 177, 5, 47, 197, 203, 25, 113, 197, 174, 29, 156, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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