Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9d90b2bcb5aef6db0895d7c80eb387cf70f45daa0ab77cbacea6f8356ba9dd2

Tx prefix hash: a30b9dc8b6c8b85dde228f10db044897d602da30d93b396d85863b53f86e2ab0
Tx public key: 2fa1846c21a99513e855a46fb59403e55fc4d815fa8ca4f5e9daacd1e95482e1
Timestamp: 1575382910 Timestamp [UTC]: 2019-12-03 14:21:50 Age [y:d:h:m:s]: 06:080:03:56:17
Block: 21297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0967 kB
Tx version: 2 No of confirmations: 1460080 RingCT/type: yes/0
Extra: 012fa1846c21a99513e855a46fb59403e55fc4d815fa8ca4f5e9daacd1e95482e1020d3930303100010000003cc89603

1 output(s) for total of 0.521717101881 xmr

stealth address amount amount idx tag
00: b62dfc9570cd4377a2ecf974da19b5cfb6fe0e0144d3c8cf7fdf0e23773969bb 0.521717101881 33942 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": 21307, "vin": [ { "gen": { "height": 21297 } } ], "vout": [ { "amount": 521717101881, "target": { "key": "b62dfc9570cd4377a2ecf974da19b5cfb6fe0e0144d3c8cf7fdf0e23773969bb" } } ], "extra": [ 1, 47, 161, 132, 108, 33, 169, 149, 19, 232, 85, 164, 111, 181, 148, 3, 229, 95, 196, 216, 21, 250, 140, 164, 245, 233, 218, 172, 209, 233, 84, 130, 225, 2, 13, 57, 48, 48, 49, 0, 1, 0, 0, 0, 60, 200, 150, 3 ], "rct_signatures": { "type": 0 } }


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