Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7a2045c4ebeb30b9b84ea7f2f24835ab11aa90a60eb0e9b7f98947499376e2a

Tx prefix hash: 6faf7013db720714df2695ee4c29e010681948f81433792673a8ece1f393c332
Tx public key: 3c846eaae2a65974335c011b3a11057aa1f45acd647b9139f2118434f64c79e4
Timestamp: 1579680586 Timestamp [UTC]: 2020-01-22 08:09:46 Age [y:d:h:m:s]: 06:028:00:49:48
Block: 50870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1428781 RingCT/type: yes/0
Extra: 013c846eaae2a65974335c011b3a11057aa1f45acd647b9139f2118434f64c79e40211000000074ac5aa02000000000000000000

1 output(s) for total of 0.416339297009 xmr

stealth address amount amount idx tag
00: 88378eb597c3c9b8a14e6c15e0d2fbe3c1caae55030dff614ac39f92d706a153 0.416339297009 94359 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": 50880, "vin": [ { "gen": { "height": 50870 } } ], "vout": [ { "amount": 416339297009, "target": { "key": "88378eb597c3c9b8a14e6c15e0d2fbe3c1caae55030dff614ac39f92d706a153" } } ], "extra": [ 1, 60, 132, 110, 170, 226, 166, 89, 116, 51, 92, 1, 27, 58, 17, 5, 122, 161, 244, 90, 205, 100, 123, 145, 57, 242, 17, 132, 52, 246, 76, 121, 228, 2, 17, 0, 0, 0, 7, 74, 197, 170, 2, 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