Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd52de2e2d9d7bd088c0c8a1c0b0fd8d421a91ed60d61a907cfe6ceb9f8c5524

Tx prefix hash: a20453b3b307a6398aa30ad27a9dd1c2f6bda93e00fcc943b1efd97009056ef3
Tx public key: 9a0918cf0449230e8d95fd3d3549407565321c71acd1e349ffcafca9fd61e740
Timestamp: 1579215662 Timestamp [UTC]: 2020-01-16 23:01:02 Age [y:d:h:m:s]: 06:035:05:37:58
Block: 47123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1433846 RingCT/type: yes/0
Extra: 019a0918cf0449230e8d95fd3d3549407565321c71acd1e349ffcafca9fd61e7400211000000044943cd9f000000000000000000

1 output(s) for total of 0.428413133841 xmr

stealth address amount amount idx tag
00: 33b07279c414a2e6ebbe34ff070fe2f55f7b0ee677d2f407ab7ea3db939ffd50 0.428413133841 87052 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": 47133, "vin": [ { "gen": { "height": 47123 } } ], "vout": [ { "amount": 428413133841, "target": { "key": "33b07279c414a2e6ebbe34ff070fe2f55f7b0ee677d2f407ab7ea3db939ffd50" } } ], "extra": [ 1, 154, 9, 24, 207, 4, 73, 35, 14, 141, 149, 253, 61, 53, 73, 64, 117, 101, 50, 28, 113, 172, 209, 227, 73, 255, 202, 252, 169, 253, 97, 231, 64, 2, 17, 0, 0, 0, 4, 73, 67, 205, 159, 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