Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17648a3098a7c194922865a5f57271c217a7d470e41eb8b8469a5d394cca4bec

Tx prefix hash: 99dc340e43a653e92c7f912006593e2d079cb8aff59e12da877960f0e70ab4fd
Tx public key: 04f44cc17c25ed4baafd357368e5eab55be9f61bb37466e3cc0463e92af057cb
Timestamp: 1577739469 Timestamp [UCT]: 2019-12-30 20:57:49 Age [y:d:h:m:s]: 04:364:19:28:11
Block: 35321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1149803 RingCT/type: yes/0
Extra: 0104f44cc17c25ed4baafd357368e5eab55be9f61bb37466e3cc0463e92af057cb021100000015c3a1a09f000000000000000000

1 output(s) for total of 468.778536707000 dcy

stealth address amount amount idx
00: a1bc8189b15fc70fee1832a3aa9a42de4580d5efe82199f5bde86d9aa66f84a7 468.778536707000 59495 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": 35331, "vin": [ { "gen": { "height": 35321 } } ], "vout": [ { "amount": 468778536707, "target": { "key": "a1bc8189b15fc70fee1832a3aa9a42de4580d5efe82199f5bde86d9aa66f84a7" } } ], "extra": [ 1, 4, 244, 76, 193, 124, 37, 237, 75, 170, 253, 53, 115, 104, 229, 234, 181, 91, 233, 246, 27, 179, 116, 102, 227, 204, 4, 99, 233, 42, 240, 87, 203, 2, 17, 0, 0, 0, 21, 195, 161, 160, 159, 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