Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ada4e4045285764d11ec326dbd91db0242da356a4df909d1707415ee5dfd693

Tx prefix hash: 47615dcb95a2b8d48bfb560a021af93a4254bd9d65bd7b33860b2f549b0dd7e8
Tx public key: 899fdcb037598f454ced294684022861c166fda96f25569805986f08b36b521c
Timestamp: 1577692302 Timestamp [UTC]: 2019-12-30 07:51:42 Age [y:d:h:m:s]: 06:077:19:41:48
Block: 34856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1463957 RingCT/type: yes/0
Extra: 01899fdcb037598f454ced294684022861c166fda96f25569805986f08b36b521c0211000000124943cd9f000000000000000000

1 output(s) for total of 0.470444567405 xmr

stealth address amount amount idx tag
00: 8779926446b0ee6a5675986eace2925d0cb420ef1a4a3e4ccf44509e9625bb86 0.470444567405 58729 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": 34866, "vin": [ { "gen": { "height": 34856 } } ], "vout": [ { "amount": 470444567405, "target": { "key": "8779926446b0ee6a5675986eace2925d0cb420ef1a4a3e4ccf44509e9625bb86" } } ], "extra": [ 1, 137, 159, 220, 176, 55, 89, 143, 69, 76, 237, 41, 70, 132, 2, 40, 97, 193, 102, 253, 169, 111, 37, 86, 152, 5, 152, 111, 8, 179, 107, 82, 28, 2, 17, 0, 0, 0, 18, 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