Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4d0988059433b653e00587cad6babfbd1dccaac0f7263a5abb9e5751ad29a76

Tx prefix hash: 2368aeec2e1eb5a1453b5b50694ce3b2d0f9986891f1627d30931db51da59aac
Tx public key: 717d909bda4eb5671837115b55636e23ed1e4139b679a44a929bd3ab1a609b7c
Timestamp: 1579189891 Timestamp [UTC]: 2020-01-16 15:51:31 Age [y:d:h:m:s]: 06:224:11:30:48
Block: 46922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1574948 RingCT/type: yes/0
Extra: 01717d909bda4eb5671837115b55636e23ed1e4139b679a44a929bd3ab1a609b7c02111f6bf7ab00000000000000000000000000

1 output(s) for total of 0.429124135444 xmr

stealth address amount amount idx tag
00: 38d92554e7357a53df256941e2315c853b135f3ec2174a1ca24d555025131f39 0.429124135444 86548 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": 46932, "vin": [ { "gen": { "height": 46922 } } ], "vout": [ { "amount": 429124135444, "target": { "key": "38d92554e7357a53df256941e2315c853b135f3ec2174a1ca24d555025131f39" } } ], "extra": [ 1, 113, 125, 144, 155, 218, 78, 181, 103, 24, 55, 17, 91, 85, 99, 110, 35, 237, 30, 65, 57, 182, 121, 164, 74, 146, 155, 211, 171, 26, 96, 155, 124, 2, 17, 31, 107, 247, 171, 0, 0, 0, 0, 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: