Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd7aa5f3f5e7058b0a8655a878b21da9ecbd1cbc8ff1cc5007fe8af80185d13d

Tx prefix hash: b14d2cf105386534dc85ef9bf87243707e5bcc053894abcfa4ab30b69971c41a
Tx public key: 4ac20b3973eba68fd7f85e3213a8e48f0877c95beec8aa76675309d033410e7c
Timestamp: 1699491641 Timestamp [UCT]: 2023-11-09 01:00:41 Age [y:d:h:m:s]: 01:152:20:11:55
Block: 887537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370419 RingCT/type: yes/0
Extra: 014ac20b3973eba68fd7f85e3213a8e48f0877c95beec8aa76675309d033410e7c021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.703430972000 dcy

stealth address amount amount idx
00: b5328e0c9f4b625cf569fb6ddbd8c84fa1bc32f84ed5613ba9774d6105eeb24d 0.703430972000 1343422 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": 887547, "vin": [ { "gen": { "height": 887537 } } ], "vout": [ { "amount": 703430972, "target": { "key": "b5328e0c9f4b625cf569fb6ddbd8c84fa1bc32f84ed5613ba9774d6105eeb24d" } } ], "extra": [ 1, 74, 194, 11, 57, 115, 235, 166, 143, 215, 248, 94, 50, 19, 168, 228, 143, 8, 119, 201, 91, 238, 200, 170, 118, 103, 83, 9, 208, 51, 65, 14, 124, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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