Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2174a001e3056e234b226fe49dafb61e18b7488410afe0528d0e60074e74ed1b

Tx prefix hash: e00fe546f0c7180473ecab944117b6d8cabea04020c533e0e47ba89788d5773f
Tx public key: 1c419190183e0c88c8e65988984b8d9ec243058085d20e1bc4b68947013602fb
Timestamp: 1574957225 Timestamp [UTC]: 2019-11-28 16:07:05 Age [y:d:h:m:s]: 06:068:10:01:18
Block: 19092 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1450366 RingCT/type: yes/0
Extra: 011c419190183e0c88c8e65988984b8d9ec243058085d20e1bc4b68947013602fb021100000005298ed69e000000000000000000

1 output(s) for total of 0.530568126737 xmr

stealth address amount amount idx tag
00: 32d83948ce5af2e9415a7d41fec649f5b4a4c0d48498a4f59be0d1af91ea6317 0.530568126737 29943 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": 19102, "vin": [ { "gen": { "height": 19092 } } ], "vout": [ { "amount": 530568126737, "target": { "key": "32d83948ce5af2e9415a7d41fec649f5b4a4c0d48498a4f59be0d1af91ea6317" } } ], "extra": [ 1, 28, 65, 145, 144, 24, 62, 12, 136, 200, 230, 89, 136, 152, 75, 141, 158, 194, 67, 5, 128, 133, 210, 14, 27, 196, 182, 137, 71, 1, 54, 2, 251, 2, 17, 0, 0, 0, 5, 41, 142, 214, 158, 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