Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c7f175010f44b0b8ff486768718ab510401031cc5c7f2abba9e9b99eee15be1

Tx prefix hash: e0a10e9a6826b500aa762fc0dd5c13643026fb881c51e77bf2f14a71fca774a4
Tx public key: 84038b69ba0f06f674ac989fed85f5a6671b1398e69c01337d691558d1cef859
Timestamp: 1702288575 Timestamp [UCT]: 2023-12-11 09:56:15 Age [y:d:h:m:s]: 01:166:09:33:47
Block: 910721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380101 RingCT/type: yes/0
Extra: 0184038b69ba0f06f674ac989fed85f5a6671b1398e69c01337d691558d1cef859021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e99f8a2d048e4af6d68a9aaebb331154b3309d7b6fc70e889441b7e2906e6d6 0.600000000000 1367888 of 15

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": 910731, "vin": [ { "gen": { "height": 910721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e99f8a2d048e4af6d68a9aaebb331154b3309d7b6fc70e889441b7e2906e6d6" } } ], "extra": [ 1, 132, 3, 139, 105, 186, 15, 6, 246, 116, 172, 152, 159, 237, 133, 245, 166, 103, 27, 19, 152, 230, 156, 1, 51, 125, 105, 21, 88, 209, 206, 248, 89, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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