Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4e1d1972e8b0bfc98a317cccde42226adb4fe53f8cad507c20f6c5bfec2e1a1

Tx prefix hash: 1061080540157ddfbfb6fc5799ce3b8d5af7ba6118bc3fab75784df41a30cf24
Tx public key: 71851cbaf9e3d42020fd4c8ae35b0a6c1ace4aa60e0545655003d0c3481f421f
Timestamp: 1577527195 Timestamp [UTC]: 2019-12-28 09:59:55 Age [y:d:h:m:s]: 06:053:01:56:52
Block: 33358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1446386 RingCT/type: yes/0
Extra: 0171851cbaf9e3d42020fd4c8ae35b0a6c1ace4aa60e0545655003d0c3481f421f021100000079398c17aa000000000000000000

1 output(s) for total of 0.475860282251 xmr

stealth address amount amount idx tag
00: 28f1b13facb4a3bb213329d007f9990fc650fcbf26e2569e9a3e6372de921637 0.475860282251 55836 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": 33368, "vin": [ { "gen": { "height": 33358 } } ], "vout": [ { "amount": 475860282251, "target": { "key": "28f1b13facb4a3bb213329d007f9990fc650fcbf26e2569e9a3e6372de921637" } } ], "extra": [ 1, 113, 133, 28, 186, 249, 227, 212, 32, 32, 253, 76, 138, 227, 91, 10, 108, 26, 206, 74, 166, 14, 5, 69, 101, 80, 3, 208, 195, 72, 31, 66, 31, 2, 17, 0, 0, 0, 121, 57, 140, 23, 170, 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