Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 401b3c9e0fd6378cc1e85816637ff97105616fc990d3c66031a1ff647b3b61c2

Tx prefix hash: a4f686119a5d06fce7fb12fcaa4b10a0d255c058f1478189df0aa3e7023cc5ca
Tx public key: 855ae395bcb970095a4d6c66bc5fe2b461ba002c1f28c8442c4a3ae2e6db3cde
Timestamp: 1583634069 Timestamp [UCT]: 2020-03-08 02:21:09 Age [y:d:h:m:s]: 05:033:20:08:16
Block: 78364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1179627 RingCT/type: yes/0
Extra: 01855ae395bcb970095a4d6c66bc5fe2b461ba002c1f28c8442c4a3ae2e6db3cde02110000000127105131000000000000000000

1 output(s) for total of 337.557941577000 dcy

stealth address amount amount idx
00: ce040f4a3e11c0fb4f60851aee0e83ccbd4f669646a9462e93175addb8b6519a 337.557941577000 143808 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 dinasty-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": 78374, "vin": [ { "gen": { "height": 78364 } } ], "vout": [ { "amount": 337557941577, "target": { "key": "ce040f4a3e11c0fb4f60851aee0e83ccbd4f669646a9462e93175addb8b6519a" } } ], "extra": [ 1, 133, 90, 227, 149, 188, 185, 112, 9, 90, 77, 108, 102, 188, 95, 226, 180, 97, 186, 0, 44, 31, 40, 200, 68, 44, 74, 58, 226, 230, 219, 60, 222, 2, 17, 0, 0, 0, 1, 39, 16, 81, 49, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8