Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abfcdcb35b46da8aa813cc2b00b75c5fc40f5d91834a9d3e2dfd5b3c7abdb3bd

Tx prefix hash: 28b60c16cf60245faaea474cf8a926e41edbb8d7e3c5bcf2581aef60a6103c86
Tx public key: 3328180c97100cfaabb70b31e70760f87b75f6776d35fb1fd81855505487e5e3
Timestamp: 1576928599 Timestamp [UTC]: 2019-12-21 11:43:19 Age [y:d:h:m:s]: 06:064:10:28:28
Block: 29377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1453548 RingCT/type: yes/0
Extra: 013328180c97100cfaabb70b31e70760f87b75f6776d35fb1fd81855505487e5e3021100000022ad433a0b000000000000000000

1 output(s) for total of 0.490526717685 xmr

stealth address amount amount idx tag
00: f38048aed82ef3890963d4f0ed3a81e22486184d1ec701303060d5b94288cde6 0.490526717685 48211 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": 29387, "vin": [ { "gen": { "height": 29377 } } ], "vout": [ { "amount": 490526717685, "target": { "key": "f38048aed82ef3890963d4f0ed3a81e22486184d1ec701303060d5b94288cde6" } } ], "extra": [ 1, 51, 40, 24, 12, 151, 16, 12, 250, 171, 183, 11, 49, 231, 7, 96, 248, 123, 117, 246, 119, 109, 53, 251, 31, 216, 24, 85, 80, 84, 135, 229, 227, 2, 17, 0, 0, 0, 34, 173, 67, 58, 11, 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