Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 667eff496e4375da6b0b6986595403d4bcea10efbbcc781f93f5443ca8ff02e9

Tx prefix hash: 7836b37bc3d29625c939f28332d432429f7c28074686f5c0867eb7072b399914
Tx public key: 74fb298ec545b2754d063e7ff3c175034c6e81a65e1f25a3ff176b4563b30f04
Timestamp: 1580119202 Timestamp [UTC]: 2020-01-27 10:00:02 Age [y:d:h:m:s]: 06:023:06:28:42
Block: 53939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1425939 RingCT/type: yes/0
Extra: 0174fb298ec545b2754d063e7ff3c175034c6e81a65e1f25a3ff176b4563b30f0402110000004bdcee4b4d000000000000000000

1 output(s) for total of 0.406704079866 xmr

stealth address amount amount idx tag
00: 7fcbe124cb8c963f6aeb18f1a1c521ba8e474e0c5066907730b6139c98c5afe7 0.406704079866 99929 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": 53949, "vin": [ { "gen": { "height": 53939 } } ], "vout": [ { "amount": 406704079866, "target": { "key": "7fcbe124cb8c963f6aeb18f1a1c521ba8e474e0c5066907730b6139c98c5afe7" } } ], "extra": [ 1, 116, 251, 41, 142, 197, 69, 178, 117, 77, 6, 62, 127, 243, 193, 117, 3, 76, 110, 129, 166, 94, 31, 37, 163, 255, 23, 107, 69, 99, 179, 15, 4, 2, 17, 0, 0, 0, 75, 220, 238, 75, 77, 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