Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8dddb88b64a77822e4c247e11fb09f4d9da9fe3dcb47f20b46869bf1487bad4e

Tx prefix hash: c8088060ba82b31f1034561e6d04767c712e95cd8f0b3a9fdab57f85b2809014
Tx public key: cda83f1c60112eab137e2ce3ae4970086828c1e840a110ae61c88957c5054fca
Timestamp: 1648659199 Timestamp [UCT]: 2022-03-30 16:53:19 Age [y:d:h:m:s]: 02:273:07:32:29
Block: 469701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 714935 RingCT/type: yes/0
Extra: 01cda83f1c60112eab137e2ce3ae4970086828c1e840a110ae61c88957c5054fca021100000018a8c141c5000000000000000000

1 output(s) for total of 17.048487470000 dcy

stealth address amount amount idx
00: 5fd6afb0186d1509b256a310e65f7e99d6b8ed64bd1dd6627302d2aaf6e3d084 17.048487470000 888699 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": 469711, "vin": [ { "gen": { "height": 469701 } } ], "vout": [ { "amount": 17048487470, "target": { "key": "5fd6afb0186d1509b256a310e65f7e99d6b8ed64bd1dd6627302d2aaf6e3d084" } } ], "extra": [ 1, 205, 168, 63, 28, 96, 17, 46, 171, 19, 126, 44, 227, 174, 73, 112, 8, 104, 40, 193, 232, 64, 161, 16, 174, 97, 200, 137, 87, 197, 5, 79, 202, 2, 17, 0, 0, 0, 24, 168, 193, 65, 197, 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