Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db7a3f4d3698656ec952e4fd82474084e1dc76b4deef48a34beaed2b0ae857c3

Tx prefix hash: bb6692a09afa686db40d86bdf4e9299b95320e7c45b9b7c06aa57fd272bc7894
Tx public key: 3f5f14fc52402a0e9906c20b2f75675c8e8a7515b46d4557252c3aacdb757361
Timestamp: 1577485417 Timestamp [UTC]: 2019-12-27 22:23:37 Age [y:d:h:m:s]: 06:101:17:24:12
Block: 33110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1481020 RingCT/type: yes/0
Extra: 013f5f14fc52402a0e9906c20b2f75675c8e8a7515b46d4557252c3aacdb757361021100000005d81c26c0000000000000000000

1 output(s) for total of 0.476761492860 xmr

stealth address amount amount idx tag
00: c38f1548233fd896b83102a222b5910cdcbc8244376ada48b475b0777580a57d 0.476761492860 55294 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": 33120, "vin": [ { "gen": { "height": 33110 } } ], "vout": [ { "amount": 476761492860, "target": { "key": "c38f1548233fd896b83102a222b5910cdcbc8244376ada48b475b0777580a57d" } } ], "extra": [ 1, 63, 95, 20, 252, 82, 64, 42, 14, 153, 6, 194, 11, 47, 117, 103, 92, 142, 138, 117, 21, 180, 109, 69, 87, 37, 44, 58, 172, 219, 117, 115, 97, 2, 17, 0, 0, 0, 5, 216, 28, 38, 192, 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