Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fd5cb8088575577419562a4e213ba756e6218f5ae2981c2640fd90cfa577500

Tx prefix hash: c26ae2f1c78e6fd5e1ccb921f9d807d2acc5985ddf211391e79830757f7e9cc8
Tx public key: 44e3f722722d63b4c2fa9ab9ec3437d3cd23e486ab05e1c0edc215477a1cde47
Timestamp: 1710278791 Timestamp [UCT]: 2024-03-12 21:26:31 Age [y:d:h:m:s]: 00:347:19:22:21
Block: 976969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248655 RingCT/type: yes/0
Extra: 0144e3f722722d63b4c2fa9ab9ec3437d3cd23e486ab05e1c0edc215477a1cde470211000000011c2d361c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c49721e673a4f7c75174f7d33ca26b2f805e308fb9c9bc392edd96df52673ef 0.600000000000 1436970 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": 976979, "vin": [ { "gen": { "height": 976969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c49721e673a4f7c75174f7d33ca26b2f805e308fb9c9bc392edd96df52673ef" } } ], "extra": [ 1, 68, 227, 247, 34, 114, 45, 99, 180, 194, 250, 154, 185, 236, 52, 55, 211, 205, 35, 228, 134, 171, 5, 225, 192, 237, 194, 21, 71, 122, 28, 222, 71, 2, 17, 0, 0, 0, 1, 28, 45, 54, 28, 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