Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b78192bb91d163dc342dbe32931c2b25b47f4d0416c061cba6ca537e0841dea9

Tx prefix hash: 00a06161f4f2dfb3dc798eafe4fb8ec349ed5b94569ca713c1679e9ed507ec5b
Tx public key: 11e928ee70f4e8cbddeb425fac795b4cfb1590dd7e1bff233219976df8c30f6b
Timestamp: 1584294662 Timestamp [UTC]: 2020-03-15 17:51:02 Age [y:d:h:m:s]: 06:058:19:25:57
Block: 83332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1448804 RingCT/type: yes/0
Extra: 0111e928ee70f4e8cbddeb425fac795b4cfb1590dd7e1bff233219976df8c30f6b0211000000093b1b9791000000000000000000

1 output(s) for total of 0.325002930010 xmr

stealth address amount amount idx tag
00: 527ccc92fbaf3cc6eb3b49a6084be69e942e1ec03a0ab5de47ba524e1838105f 0.325002930010 151582 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": 83342, "vin": [ { "gen": { "height": 83332 } } ], "vout": [ { "amount": 325002930010, "target": { "key": "527ccc92fbaf3cc6eb3b49a6084be69e942e1ec03a0ab5de47ba524e1838105f" } } ], "extra": [ 1, 17, 233, 40, 238, 112, 244, 232, 203, 221, 235, 66, 95, 172, 121, 91, 76, 251, 21, 144, 221, 126, 27, 255, 35, 50, 25, 151, 109, 248, 195, 15, 107, 2, 17, 0, 0, 0, 9, 59, 27, 151, 145, 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) | monero version: