Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2abbcc216141135c43b1cfc7214f4a62a3e9bad800064417bea0be5c21844e2f

Tx prefix hash: b2e53e6cd8159c244059d8656995cc0aa0c8e509e7a008f8d766f48d12f3bb7a
Tx public key: c7d2df3f6ba62fa02a18ba7587d90fd2f86ef39560a7b064235e44ba09ad6e07
Timestamp: 1649692794 Timestamp [UCT]: 2022-04-11 15:59:54 Age [y:d:h:m:s]: 02:301:21:09:13
Block: 478020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 735358 RingCT/type: yes/0
Extra: 01c7d2df3f6ba62fa02a18ba7587d90fd2f86ef39560a7b064235e44ba09ad6e070211000000125eb576c5000000000000000000

1 output(s) for total of 16.000057455000 dcy

stealth address amount amount idx
00: c71c202296fccdaf8b3a1da3d74159bdf05e91ec18ad4091d09e20ed1061bf99 16.000057455000 898737 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": 478030, "vin": [ { "gen": { "height": 478020 } } ], "vout": [ { "amount": 16000057455, "target": { "key": "c71c202296fccdaf8b3a1da3d74159bdf05e91ec18ad4091d09e20ed1061bf99" } } ], "extra": [ 1, 199, 210, 223, 63, 107, 166, 47, 160, 42, 24, 186, 117, 135, 217, 15, 210, 248, 110, 243, 149, 96, 167, 176, 100, 35, 94, 68, 186, 9, 173, 110, 7, 2, 17, 0, 0, 0, 18, 94, 181, 118, 197, 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