Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6191187768c118eca4a1ca36c73740a737acb05a92f0963d4048a880bb899cfd

Tx prefix hash: a5308d7e30e9dcc87364b5d0fae661018a29fb15d94a49980a1c06ffe421f501
Tx public key: 7b0a260144c1ea0aa1e8a50632333096b0a75d508862fa4aeff15e26b31c9643
Timestamp: 1730700626 Timestamp [UCT]: 2024-11-04 06:10:26 Age [y:d:h:m:s]: 00:153:20:59:40
Block: 1146183 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109792 RingCT/type: yes/0
Extra: 017b0a260144c1ea0aa1e8a50632333096b0a75d508862fa4aeff15e26b31c9643021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf94c43022133cfa4bc5fdf23ecb08f9199da3f6608a85df87e52e6fb09e44ed 0.600000000000 1630774 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": 1146193, "vin": [ { "gen": { "height": 1146183 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf94c43022133cfa4bc5fdf23ecb08f9199da3f6608a85df87e52e6fb09e44ed" } } ], "extra": [ 1, 123, 10, 38, 1, 68, 193, 234, 10, 161, 232, 165, 6, 50, 51, 48, 150, 176, 167, 93, 80, 136, 98, 250, 74, 239, 241, 94, 38, 179, 28, 150, 67, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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