Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fba273c39ff74937ab68b09930abc9e38e377752858f9db3c1fdc0645a4b62a

Tx prefix hash: 99da2227bc85d2a735796da4c1efeeb6215cc4585a531a95ebf2692665137e7f
Tx public key: 13ef071d10d69be307fabbbde922a1e9d017ad4de99d60815bc064ad23eeffc9
Timestamp: 1724496800 Timestamp [UCT]: 2024-08-24 10:53:20 Age [y:d:h:m:s]: 00:225:21:13:08
Block: 1094846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161282 RingCT/type: yes/0
Extra: 0113ef071d10d69be307fabbbde922a1e9d017ad4de99d60815bc064ad23eeffc902110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff5e1785bb2d36a9543f1a26ebd5724e7a321e0bcf7a7ad7beb2a97fb5627508 0.600000000000 1569967 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": 1094856, "vin": [ { "gen": { "height": 1094846 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff5e1785bb2d36a9543f1a26ebd5724e7a321e0bcf7a7ad7beb2a97fb5627508" } } ], "extra": [ 1, 19, 239, 7, 29, 16, 214, 155, 227, 7, 250, 187, 189, 233, 34, 161, 233, 208, 23, 173, 77, 233, 157, 96, 129, 91, 192, 100, 173, 35, 238, 255, 201, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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