Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d61426a4972af5b54694b80fd4511542e9e7f9d549bab9ddcb8d6e7e3739fc8

Tx prefix hash: dbc53c3e554432a165fcfe86eb012276461582efa5bcd86e6db79eacd82448db
Tx public key: 9b297912033b2128f22abff3601df3be80b0ec8768e002241428ff6b1d3600be
Timestamp: 1628025519 Timestamp [UCT]: 2021-08-03 21:18:39 Age [y:d:h:m:s]: 03:107:19:25:00
Block: 306771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 849742 RingCT/type: yes/0
Extra: 019b297912033b2128f22abff3601df3be80b0ec8768e002241428ff6b1d3600be021100000016e6f80b5a000000000000000000

1 output(s) for total of 59.093649357000 dcy

stealth address amount amount idx
00: ae990f482eea386cf4a3bf0851a5038d4ad8d40543046c8603101e056c2acd5e 59.093649357000 639640 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": 306781, "vin": [ { "gen": { "height": 306771 } } ], "vout": [ { "amount": 59093649357, "target": { "key": "ae990f482eea386cf4a3bf0851a5038d4ad8d40543046c8603101e056c2acd5e" } } ], "extra": [ 1, 155, 41, 121, 18, 3, 59, 33, 40, 242, 42, 191, 243, 96, 29, 243, 190, 128, 176, 236, 135, 104, 224, 2, 36, 20, 40, 255, 107, 29, 54, 0, 190, 2, 17, 0, 0, 0, 22, 230, 248, 11, 90, 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