Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b3abcdd3290cf59e254f6dc9b033c1fbacffa5e7c7f11501c6d271859355e6c

Tx prefix hash: 68978fe52399d3ed89471706f2d1f7379e4abf1c235c1014aacd4e65b17b38b2
Tx public key: f371b4d61632aaa3812f9551ca75dacb19d894a9db133ae3da3823990be3d6fc
Timestamp: 1712200711 Timestamp [UCT]: 2024-04-04 03:18:31 Age [y:d:h:m:s]: 01:038:14:31:59
Block: 992861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288601 RingCT/type: yes/0
Extra: 01f371b4d61632aaa3812f9551ca75dacb19d894a9db133ae3da3823990be3d6fc02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 761e1f18bf3c74c59eae7203f7602353069a7b7e1a7102449401fc5eea2993e9 0.600000000000 1453237 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": 992871, "vin": [ { "gen": { "height": 992861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "761e1f18bf3c74c59eae7203f7602353069a7b7e1a7102449401fc5eea2993e9" } } ], "extra": [ 1, 243, 113, 180, 214, 22, 50, 170, 163, 129, 47, 149, 81, 202, 117, 218, 203, 25, 216, 148, 169, 219, 19, 58, 227, 218, 56, 35, 153, 11, 227, 214, 252, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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