Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6a1381b81896ec4a448033a104d0bb75a8d1ab560f6c0f299c8f9c5c4c30ca6

Tx prefix hash: 03512fbfbc4d9b6087743256373979051fb2739c14bc35f0309137f64e31d2e2
Tx public key: 48a08e45700117a1c22cf5c176fc67473c84f0aef270f85da138d3e7b328baf2
Timestamp: 1727636917 Timestamp [UCT]: 2024-09-29 19:08:37 Age [y:d:h:m:s]: 01:043:23:57:28
Block: 1120864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289846 RingCT/type: yes/0
Extra: 0148a08e45700117a1c22cf5c176fc67473c84f0aef270f85da138d3e7b328baf202110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e1901e44ad13d7c56e1987dcf84cadb5e49d3f2dbb75a40cf3f4c96a5824270 0.600000000000 1602935 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": 1120874, "vin": [ { "gen": { "height": 1120864 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e1901e44ad13d7c56e1987dcf84cadb5e49d3f2dbb75a40cf3f4c96a5824270" } } ], "extra": [ 1, 72, 160, 142, 69, 112, 1, 23, 161, 194, 44, 245, 193, 118, 252, 103, 71, 60, 132, 240, 174, 242, 112, 248, 93, 161, 56, 211, 231, 179, 40, 186, 242, 2, 17, 0, 0, 0, 2, 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