Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3dc84a2b25f7117f1933c84e132e8c3b3c025b6e31f47006478a340e8364fa94

Tx prefix hash: a3eaef0ddd92ab5e8263ffa09baa6577bfc4ee0912731234ded1cdd192c7d3ff
Tx public key: 4acc42ea2d0aa64906610db2de5d7009606a6eb4a21d249854897772b3b847d1
Timestamp: 1719114922 Timestamp [UCT]: 2024-06-23 03:55:22 Age [y:d:h:m:s]: 00:290:15:59:11
Block: 1050202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207715 RingCT/type: yes/0
Extra: 014acc42ea2d0aa64906610db2de5d7009606a6eb4a21d249854897772b3b847d10211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64830e315ae50d5433f374a1d4241f2d0678fbc2f55a5e6da59176efdad93a60 0.600000000000 1520363 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": 1050212, "vin": [ { "gen": { "height": 1050202 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64830e315ae50d5433f374a1d4241f2d0678fbc2f55a5e6da59176efdad93a60" } } ], "extra": [ 1, 74, 204, 66, 234, 45, 10, 166, 73, 6, 97, 13, 178, 222, 93, 112, 9, 96, 106, 110, 180, 162, 29, 36, 152, 84, 137, 119, 114, 179, 184, 71, 209, 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