Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ec719c81c39a7ac5668e461a3bf0bc79d6424ce8f0d57c2dcbb429ac164753b

Tx prefix hash: c407c71718bcd7399cf8a15f527a847d7a87eaf433f4bac31251b1ff3ecc3647
Tx public key: 849c520467640682486b4aeb8b6fef41ce92a6a1e753f9874486c74198f7b12e
Timestamp: 1576526532 Timestamp [UTC]: 2019-12-16 20:02:12 Age [y:d:h:m:s]: 06:342:00:53:30
Block: 27929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1655565 RingCT/type: yes/0
Extra: 01849c520467640682486b4aeb8b6fef41ce92a6a1e753f9874486c74198f7b12e02110000001ad81c26c0000000000000000000

1 output(s) for total of 0.495984368947 xmr

stealth address amount amount idx tag
00: 7f02156f1f032ff1a2dffeb05f3885df8c6e86274b97743ec2657143cc021240 0.495984368947 46209 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": 27939, "vin": [ { "gen": { "height": 27929 } } ], "vout": [ { "amount": 495984368947, "target": { "key": "7f02156f1f032ff1a2dffeb05f3885df8c6e86274b97743ec2657143cc021240" } } ], "extra": [ 1, 132, 156, 82, 4, 103, 100, 6, 130, 72, 107, 74, 235, 139, 111, 239, 65, 206, 146, 166, 161, 231, 83, 249, 135, 68, 134, 199, 65, 152, 247, 177, 46, 2, 17, 0, 0, 0, 26, 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) | monero version: