Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bb881e24e338da128a1e6dc8c5d177e51a93c630041df70606e51c84fe6a956

Tx prefix hash: 5dcfb02a7f66d64ff9ba529e895c142f8822f4962c302a96a40e6e58f18af1ba
Tx public key: 308d7c86075f3ad33ea2291738326db7f2c2f100b5e2fc376090225c600796ac
Timestamp: 1578272976 Timestamp [UTC]: 2020-01-06 01:09:36 Age [y:d:h:m:s]: 06:044:15:41:53
Block: 39524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1440358 RingCT/type: yes/0
Extra: 01308d7c86075f3ad33ea2291738326db7f2c2f100b5e2fc376090225c600796ac021100000001b221b3d1000000000000000000

1 output(s) for total of 0.453984922075 xmr

stealth address amount amount idx tag
00: 57a21da5141da0b3d60f3cfa08c9b6ec0450f2578a67405eeb84c627c174cb73 0.453984922075 68334 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 dinastycoin-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": 39534, "vin": [ { "gen": { "height": 39524 } } ], "vout": [ { "amount": 453984922075, "target": { "key": "57a21da5141da0b3d60f3cfa08c9b6ec0450f2578a67405eeb84c627c174cb73" } } ], "extra": [ 1, 48, 141, 124, 134, 7, 95, 58, 211, 62, 162, 41, 23, 56, 50, 109, 183, 242, 194, 241, 0, 181, 226, 252, 55, 96, 144, 34, 92, 96, 7, 150, 172, 2, 17, 0, 0, 0, 1, 178, 33, 179, 209, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369