Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09b30b5a4fa5789d3a88a88312f75813c7459070b3813a549708d5c167c534dc

Tx prefix hash: 3528df252aafc3a669341cc9b4beba5443342f9bba56e97373f66c8a4beffe56
Tx public key: 3a1e3d0cb67a7524f494a213fb0f668fa0551b1c840ac63ba53cdc1d5a689c7f
Timestamp: 1662154644 Timestamp [UCT]: 2022-09-02 21:37:24 Age [y:d:h:m:s]: 02:235:18:03:09
Block: 579479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 689766 RingCT/type: yes/0
Extra: 013a1e3d0cb67a7524f494a213fb0f668fa0551b1c840ac63ba53cdc1d5a689c7f021100000002e4c64a6f000000000000000000

1 output(s) for total of 7.378118207000 dcy

stealth address amount amount idx
00: 3bfb0e4b58c06dab8a0e70f76892a4fe461970e6501f22060fd9077d4bd5c5e9 7.378118207000 1012939 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": 579489, "vin": [ { "gen": { "height": 579479 } } ], "vout": [ { "amount": 7378118207, "target": { "key": "3bfb0e4b58c06dab8a0e70f76892a4fe461970e6501f22060fd9077d4bd5c5e9" } } ], "extra": [ 1, 58, 30, 61, 12, 182, 122, 117, 36, 244, 148, 162, 19, 251, 15, 102, 143, 160, 85, 27, 28, 132, 10, 198, 59, 165, 60, 220, 29, 90, 104, 156, 127, 2, 17, 0, 0, 0, 2, 228, 198, 74, 111, 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