Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa5a5f676e291476febd85c59f2db9ce9cba1aeda50fe9ef79df547cae8af9bc

Tx prefix hash: 1e9b0f873018482a2a9b48ff2b1997de12b11d613897685fa92c0b19da7fc734
Tx public key: 7fbcea2a70ead6862650c876d17bfc80bdaf78d0ee91a05a10eec37dce0fae46
Timestamp: 1695451145 Timestamp [UCT]: 2023-09-23 06:39:05 Age [y:d:h:m:s]: 01:188:01:15:24
Block: 854232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395458 RingCT/type: yes/0
Extra: 017fbcea2a70ead6862650c876d17bfc80bdaf78d0ee91a05a10eec37dce0fae460211000000024b8f5122000000000000000000

1 output(s) for total of 0.906932209000 dcy

stealth address amount amount idx
00: ab1a46ba08d8f0547778122718383f909c3a3d23cfb98d2d4ca13ad16cee964a 0.906932209000 1308198 of 0

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": 854242, "vin": [ { "gen": { "height": 854232 } } ], "vout": [ { "amount": 906932209, "target": { "key": "ab1a46ba08d8f0547778122718383f909c3a3d23cfb98d2d4ca13ad16cee964a" } } ], "extra": [ 1, 127, 188, 234, 42, 112, 234, 214, 134, 38, 80, 200, 118, 209, 123, 252, 128, 189, 175, 120, 208, 238, 145, 160, 90, 16, 238, 195, 125, 206, 15, 174, 70, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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