Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2d1748ce341d631c97ecd10da8a369abb21a478bcd459541b851d7c798246b6

Tx prefix hash: bb43bd43f8abe45da39198ba46340e233ea3b4cd2c516c66930b08634ffd29f9
Tx public key: 4fbf6358ae2525ead26ca46032897c529b1138acb8aa4de855b6811ee377806b
Timestamp: 1659938633 Timestamp [UCT]: 2022-08-08 06:03:53 Age [y:d:h:m:s]: 02:250:12:17:41
Block: 561199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 700256 RingCT/type: yes/0
Extra: 014fbf6358ae2525ead26ca46032897c529b1138acb8aa4de855b6811ee377806b021100000002ec6d1a1a000000000000000000

1 output(s) for total of 8.482324134000 dcy

stealth address amount amount idx
00: a3fdf2b723872e2fb665e87fbb813c095f8947fdfe9e4c946d75197762760274 8.482324134000 993491 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": 561209, "vin": [ { "gen": { "height": 561199 } } ], "vout": [ { "amount": 8482324134, "target": { "key": "a3fdf2b723872e2fb665e87fbb813c095f8947fdfe9e4c946d75197762760274" } } ], "extra": [ 1, 79, 191, 99, 88, 174, 37, 37, 234, 210, 108, 164, 96, 50, 137, 124, 82, 155, 17, 56, 172, 184, 170, 77, 232, 85, 182, 129, 30, 227, 119, 128, 107, 2, 17, 0, 0, 0, 2, 236, 109, 26, 26, 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